home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
MacWorld 1998 October
/
Macworld (1998-10).dmg
/
Shareware World
/
Utilities
/
Data & Time Management
/
Pardeikes Welcome Plugin 2.0
/
Version History
< prev
next >
Wrap
Text File
|
1998-07-24
|
31KB
|
883 lines
Pardeikes Welcome Plugin 2.0
======================
Version History
____________________________________________________________
What's new in 2.0:
I just decided to call it 2.0 instead of 1.6 to reflect all these
new changes.
Bug Fixes & Improvments:
- Removed a bug in the rule converting code.
- Added a monitoring call: http://www.foo.com/monitor.welcome
- Minor changes to the getRule and setRule calls.
____________________________________________________________
What's new in 1.6b23:
Since I have rewritten the internal format for all
configuration files, I need to test again. So many things
have changed, hopefully you understand that I cannot
rely on beta 22 testing (which was really good).
Here are the new features:
• NEW LOG FORMATS!!
Rules and Hosts are now saved as tab-text files. You can
(and should) use the supplied Filemaker Pro 4.0 database
templates to import/export data from the files "Welcome Hosts"
and "Welcome Rules". All converting is done the first time you
start Welcome, so you don't have to do it yourself. Please make
backups before starting Welcome.
• New external log saving!
In any rule, you can now define a path to a log file. Also,
you define some text that is added to that file. Use the two
new fields below the "Mode" field: "Append to file:" and
"Append this text:" for that.
The path uses "/" to separate folders and you can use wildcard
results in this field to make it a dynamic path. Any non-existant
folders will be created by Welcome. It is a root relative path
and should start with a "/" (like the "Path:" field).
The appended text can also use wildcards (only this makes
sense at all) and here is a list of additional strings you can
use in this field as well:
\t - tab
\r - return
\n - newline
\#nnn - ascii character nnn (decimal)
\d - macintosh formatted date (can be imported to filem.)
\h - macintosh formatted time (can be imported to filem.)
\1 - seconds (two digits)
\2 - minutes (two digits)
\3 - hours (two digits)
\4 - day (two digits)
\5 - day of week, and sunday = 0 (two digits)
\6 - month (two digits)
\7 - year (two digits)
Example: Something that will log any referer to an image on
your site (only if the referrer is not yourself):
Name: Log Graphic-Referers
Path: *.{gif jpg}
Referrer: http://www.yourserver.com*
"Referer" : * <- use the custom field
Condition: <P0>&<!R0>&<C0>
Append to file: /<P2>-grabbers.txt
Append this text: \d\t\h\t<P0>\t<C1>\r
• Extended "Jump to:" field
You can now use "=n" to jump to rule n and "+d" to jump
forward (0 is current rule, 1 is next rule...) and "-d" to
jump backwards (0 is current rule, -1 is previous rule...)
Of course, "stop" and any rule name will continue to work
in this field.
• Folder creation
Either the "External-Referrer Log" or the "Error Log"
will now create any subfolders if they are not present.
____________________________________________________________
What's new in 1.6b22:
Bug Fixes & Improvments:
Version 1.6b21 was actually not the real last beta 21.
It does not include the fix for the corrupted count file.
It also does not fix the custom color bug on the gif
statistics. All these potential changes are present in
1.6 beta 22.
• Fixed a bug, where the Referrer field at the test
page where not working.
• You can now have the six wildcard fields to be case-
sensitive. Just check the checkboxes, that are located
below those 6 fields.
____________________________________________________________
What's new in 1.6b21:
Bug Fixes & Improvments:
• Fixed a crash when clicking on "Clear Hit Counter"
while it was not enabled at all.
• Probably fixed the bug with corrupted Count File.
Welcome now opens/closes the file every time it needs
to update information. If an error occurs, it will just
not update the info, but simply continues...
If Welcome is starting with a corrupted Count File
anyway, it will just stop updating it until you remove
the corrupted file. In that case, it will create a new
one without a server restart.
• Fixed a color bug, where colors got mixed up on the
graphical statistic when someone used custom colors
on "Overall" or with a unknown host name.
• Now you can send 301 and 302 redirect messages.
At the rule page, there is a "Redirect temporary" and
a "Redirect permanent" radio button.
• On public demand, I have reversed the order of the
counting statistics. Older dates are at the end of the
list.
• You can now use
<!--#exec piservice="WELCOME_#" param="cmds"-->
to insert specific values out of every counting stats into
a SSI page.
"cmds" is of format "virtualhostname/s/i/k"
where s is either "0,-1,...,-7" or "d" or "m" and i is the
index of the table line (i.e. i = 0 means first
line in table) and k is either "h","b","e" or "u"
(Hits,Bytes,Errors,Users)
Example: param="www.test.de/m/8/b" will use the
9th line out of the monthly table of "www.test.de" to
get the bytes transfered.
Still to do:
Make wildcard matching case-sensitive on demand.
____________________________________________________________
What's new in 1.6b20:
Bug Fixes & Improvments:
• New memory scheme that will work better with many
hosts (previous more than about 70 hosts and enabling
stats and hit counters will give you trouble)
• If you set an ALLOW filter for the pi_admin realm,
Welcome was not accessable from that IP number.
Now, if you set e.g. ALLOW 128.23.5.88. for the
pi_admin realm, you can access pi_admin.welcome
from the computer with ip=128.23.5.88
Beta 19 already did this, but I forgot the ending dot
in the IP address. For security reasons, Welcome
will only detect FULL ip allows and no ranges of IPs...
• PRIV log entries are not counted as ERR anymore
• If you have more hosts defined in the "Welcome Data"
file than you have set as a maximun at the prefs page,
Welcome now handles this correctly (previous, the last
possible host was corrupted...)
• You can now use Rule Result: MY_REALM/folder/aPage
to display a password dialog for MY_REALM and if the
user clicks cancel, Welcome will send /folder/aPage
(relative to the server root). So you are now able to
have your own "Access denied" pages. BTW: you can
use wildcard references to create that path. Example:
Rule Result: MY_REALM<P1>/deny.txt
____________________________________________________________
What's new in 1.6b19:
Bug Fixes:
• Welcome is now fully compatible with NITRO ULTRA.
• Wildcards are now encoded correctly if you use
pi.admin.welcome&getrule=n
• Welcome was adding ASCII 0 characters to the referer
and error logs. Thus you were not able to read the full
file. This is fixed now. Each line ends in a simple ASCII 13
and if your browser displays the log in one big line without
line breaks, you should use a different file name or file
suffix for the logs. Beta 17 was ending each line with
ASCII 13 - ASCII 10 but to be more compatible with
databases, beta 18 removed the ASCII 10 but I forgot
to reduce the number of written bytes, thus a ASCII 0
was added to the end of each line.
• Now Welcome does not encode/decode + in the search args
or path args anymore. Thus e.g. ..../?name=ab+cd&age=7
is handled fine. However, + in the path portion will be
decoded to spaces, because some users have file names
that contain spaces (e.g. www.host.com/ab+cd/foo.html
and a folder called "ab cd").
• "Hide subfolders if possible" now removes the subfolder
with a redirect ONLY if the current request is not a POST
request. Prior, the post arguments were not send again when
the browser was receiving a redirect - thus they were lost.
• If you have Allow/Deny addresses set for the pi_admin
realm, Welcome was complaining about a missing realm.
Now Welcome accepts calls to pi_admin realm that are
not restricted by uses of allow's to that realm. For security
reasons, you can only define allow's for full IP numbers!!
(ALLOW * or ALLOW www.somehost.com or ALLOW 195.*
will NOT WORK, only ALLOW n.n.n.n with n=0...255)
____________________________________________________________
What's new in 1.6b18:
Bug Fix:
• Several small cosmetic bug fixes.
New & Improved:
• Welcome uses the information from multihoming software
like Starnines VH plugin to set the correct Host: entry and
route hits to its own host set-up.
• Some pages (mostly the prefs page) were cleaned up and
some comments were added.
• The 3 beeps per minutes were removed. Most users were
annoyed by this, however I hope that I can trust people to
really pay for my product and support. Remember: a pizza
may cost 20 bucks and does nothing for your server ... :-)
• A dialog, that works with every browser, was added to
inform unregistered users about the 7-days-in-sequence
testing restriction.
• Statistics were renamed to avoid confusion. The statistics
now split into two seperate features:
a) Activity Graph and b) Hit Counters
• You can use Welcome to create realtime statistics even if
you don't use Welcome for multihoming or virtual hosting.
For this, a new checkbox: (x) Ignore not configured hosts
was added to the prefs page. It will allow you to only use
the host definition pages in Welcome for defining statistics.
For this to work, do the following:
- Check "Ignore not configured hosts" at the prefs page
- Add every host to Welcome that you like to count stats for
- Leave the subfolder for that host empty!
- Set the index file to "None"
- Se the slash handling to "Never"
- Enable the statistics options: Activity Graph & Hit Counters
• The text page that was returned from
/pi_admin.welcome?getrule=n was modified so it contains
the field names and is better readable.
____________________________________________________________
What's new in 1.6b16 + 1.6b17:
Bug Fix:
• Custom tags got corrupted between calls. After I made
these values local to the current request, this is fixed now.
Beta 17 fixes one small bug left in beta 16.
____________________________________________________________
What's new in 1.6b15:
Bugs & Fixes
=========
Bug Fix:
• Logging of errors and referer now works independand
to counting statistics. Before, both logs were only created
when Counting Stats were enabled. In beta 14, I forget to
tell that the paths for both files are SERVER root relative.
• Some users report crashes when switching from older
version to beta 14. This was not reproducable by me, so
please report it if it happens to you too.
Changed and New:
• Graphical stats now have only one url -> stats.welcome.
Calling "pi_admin_stats.welcome" was replaced by
"stats.welcome" - Welcome now protects it with the pi_admin
password themself. This was done to reduce the number of calls.
• If Welcome is used with AppleShareIP, security is preserved
by defining a custom pi_admin password in Welcome. As ASIP
does not support REALMS, Welcome defines its own protecting
password (for accessing ....pi_admin.welcome....)
For access, you need to create a file called "Welcome Password"
inside the "Welcome-Plugin ƒ" folder. Put a name:password
line into it and Welcome reads it when the server is starting.
Without this file, access to Welcome is denied.
• For other servers than AppleShareIP, Welcome checks if
a REALM pi_admin is defined. If not, Welcome cannot be
accessed.
• Some users have virtual subfolders like "/myfolder/".
Welcome now correct these entries to "/myfolder" to prevent
double "//" inside the url.
____________________________________________________________
What's new in 1.6b14:
Beta 14 will last until 30th April. It is the final
beta and if no bugs or major suggestions reach me,
it will become the final 1.6 version.
Bugs & Fixes
=========
Bug Fix:
• Fixed crashes with 68k WebSTAR 1.3.2 (its not my fault,
WebSTAR 1.3.2 does not handle some parameters correctly)
Changed and New:
• There are two new fields at the host page. You can use
them to create log files for
a) external referers (that is, referer is not yourself)
b) errors
If you put root relative paths (like :myfolder:errors.txt)
into it, Welcome will create those files and append any new
data. I have added two FileMaker Pro templates, so you can
easily import those files.
Format of a)
Date<tab>Time<tab>External-Referer<tab>Current-Path<CR><LF>....
Format of b):
Date<tab>Time<tab>Error-Path<tab>Referer<CR><LF>....
• The graphical stats now have a correct and meaningful
vertical scale. The units are displayed right next to the
axis. Due to this change, the stats format has changed, so
you will loose your last (graphical) stats if you install
beta 14. Sorry.
• The counting stats tables can now have custom header
names. Just use this format:
.../count.welcome?[#,d,m]/[colors]/n1,n2,n3,n4
where
n1 = name instead of "Hits"
n2 = name instead of "Bytes"
n3 = name instead of "Erors"
n4 = name instead of "Users"
Note, that n1...n4 can only be 16 characters max. each.
• The test page has one new field where you can put your
custom HTTP header lines. E.g. you can put the following
into it:
Authorization: Basic [putBase64EncodedPasswordhere]
Accept: html/text, */*
Note. You cannot put a real name:password combination
after Authorization, because you are simulating a http
header, you need to encode it. The simplest way to get this
is to use your browser to accees e.g. pi_admin.... and set
the "Verbose Mode" of WebSTAR to "On". Then watch the
log while you enter a password and finally click cancel
or type it in correctly. You should find a encoded string
of your name:password in the log.
____________________________________________________________
What's new in 1.6b13:
Bugs & Fixes
=========
Bug Fix:
• Saving the graphical stats to a temporary file has been
fixed. Before, Welcome could crash if someone had changed
the Welcome Data file so it got out of sync with the temp
file.
• Two small bugs were fixed that could cause crashes on
startup and when entering new hosts.
• Stats tables are now HTML encoded if necessary.
Changed and New:
• Welcome now reloads the external files (the file that
start with #) automatically every minute if they have
been changed. No need to call reload.welcome to update
any changes to those files.
• You can now define for each virtual host whether the stats
are counted separate for this host or if they are counted
to the "primary" host. A primary host is the first (from top)
virtual host that has the same subfolder.
• There is a new function for the Missing Host path on the
prefs page. If you put "pass" (without "") in the field,
Welcome will simply ignore any not configured virtual
host requests. That is very helpful when using Welcome
for statistics, rules and multiple index files if you are
using another virtual hosting solution (e.g. FireSite, W* 3.0
or ClearlyHome). In this case, you need to leave the virtual
subfolder of every host you define in Welcome empty.
____________________________________________________________
What's new in 1.6b12:
Bugs & Fixes
=========
Bug Fix:
• A bug, with bytes_send > 4 GB not calculated correctly
was fixed. Also bars for those values are now correct.
• Welcome now checks the 'vers' resource to determine
if it is installed on WebSTAR 1.3.2 to prevent a crash
if the logging is registered with WebSTAR 1.3.2.
Changed:
• Welcome now works with ASIP. To use hit
counting, Welcome needs to be configured in ASIP as a
postprocessor.
• Welcome now uses GIF format instead of JPEG. This
will free more memory and makes it compatible with
ASIP. You don't need QuickTime anymore. As a result
of this, the call for graphical stats has changed. It does
not contain the quality flag anymore:
..../stats.welcome?[host name here] or
..../pi_admin_stats.welcome?[host name here]
As a result, the final graphic is only around 2K of size!
• You can add your own color layout for either the
graphical stats or the hit counters. Append the following
hex colors to the known calls:
..../count.welcome?[host name]/[selector]/[colors1]
and
..../stats.welcome?[host name]/[colors2] or
..../pi_admin_stats.welcome?[host name]/[colors2]
Use a sequence of hex colors (000000 - FFFFFF) in
each [color1] and [color2] which are defined as:
[color1] = BBBBBBTTTTTTFFFFFFIIIIIIXXXXXXAAAAAA
and B = Background, T = Title, F = Frame, I = Inside,
X = Text and A = Bars
[color2] = BBBBBBLLLLLL111111222222FFFFFF
and B = Background, L = Labels, 1 = Inside1, 2 = Inside2
and F = Inner frame
Examples: (Colors same as built-in colors)
..../stats.welcome?www.abc.com/999999000000CCCCCCFFFFFFFFFFFF
..../count.welcome?www.abc.com/d/FFFFFF999999CCCCCCFFFFCC000000FF0000
• You can now use the counting tables inside SSI. To insert
them into your SSI parsed page, you can use the following
syntax:
<!--#exec piservice="WELCOME_STATS" param="xxxxxx"-->
and replace xxxxxx with the stuff you would write after the ?
in the normal call. To insert the example call from above, you
would write:
<!--#exec piservice="WELCOME_STATS" param="www.abc.com/d/FFFFFF999999CCCCCCFFFFCC000000FF0000"-->
You can place more than one #exec call in the same page to get more
than one table shown.
Still do to:
• Custom protection for ASIP's PI_ADMIN realm
• Allow to disable the "Missing Host page", so users can
use Welcome to count stats with other virtual hosting
plugins or servers. Currently, defining all hosts to
count with a empty subfolder will do too, but only
works if ALL hosts are configured. To prevent errors
for not configured hosts, we need a "disable it" feature.
____________________________________________________________
What's new in 1.6b11:
Bugs & Fixes
=========
New: Welcome now supports logging for QuidProQuo.
However, you will need to configure QPQ for this. Go
to the Pre/Postprocessor setup of QPQ and enter
".welcome" as a Preprocessor (without the ""). Due
to a bug in QPQ 2.1, Welcome will not count Bytes
and Errors. I am working closly with the developer
of QPQ to make this easier and better for you. He said
he is working on 2.1.1 - which should be fully compatible
with Welcome.
New: Welcome now supports WebSTAR 1.3.2 for logging
too. Just go to the Pre/Postprocessor section in the
WebAdmin (misc settings) and set the Postprocessor
to ".welcome" (without the ""). This is necessary because
WebSTAR 1.3.2 does not support the plugins logging role.
New: Welcome now counts "user visits". You can define
the time a new visit will occur by going to the prefs page
and entering a value like e.g. 300 secs = 5 minutes. So if
a user hits the site in intervals less then 5 minutes all
hits will not generate new visits.
Attention: Sorry, the count file format has changed. This
means that all your old counts will be set to zero when
using beta 11 for the first time.
New: A new setting at the prefs page (at the bottom of the
page) will control how Welcome uses its memory. Set the
max. number of virtual hosts to a value between 1...10000.
Set it low to preserve memory. Also check the "Save memory"
option if you get low memory situations. Welcome will write
most changes directly to disk thus freeing more memory.
However, this can slow down the server access by a few
milliseconds (not much in other words).
Changed: Count pages will show bars for all values and they
contain the new "Visits" count. Also the delivery of count
pages has be speeded up. They load faster.
Bug Fixes: Several small bugs were fixed. All of them
were too complicated to explain.
____________________________________________________________
What's new in 1.6b10:
Bugs & Fixes
=========
This version of Welcome is primary a bug fix release. It
fixes several internal bugs that are not worth to tell about.
Changed: Welcome now saves the hit counts linked to the
host name, not the host subfolder. You should delete the
file "Welcome Counts" before starting this release. All
old hit counts will be ignored.
____________________________________________________________
What's new in 1.6b9:
Bugs & Fixes
=========
Fixed a bug where WIDTH=0 in a gif will crash Netscape 4.0.4
Now Welcome just don't add <IMG SRC=...> if WIDTH is 0.
Fixed a bug where counters did not jump to the next day.
Fixed a bug, where clearing stats (also at startup) will corrupt
stats, so counting did not continue.
Changed the way logging checked the host. Previous Welcome
checked the virtual subfolder. Now Welcome is checking the
Host: entry instead. Virtual hosting will always add it if it
is missing, so no problem for the logging part.
Welcome now saves the overall stats periodically (like all
others, but for overall, it was missing).
Fixed some other minor and dumb bugs that may crash your
server.
Update: Welcome now dispays Bytes, KBytes and MB instead
of the pure bytes values.
Changed: To reload all Welcome data (Hosts, Rules, External
Files), you should now call ..../reload.welcome insteaf of
..../pi_admin.welcome?reload. This will put the control to
the webmaster. He/She can decide to protect this call with
a realm "reload.welcome" or make it public, so users can
call it to reload all external files.
____________________________________________________________
What's new in 1.6b8:
Bugs & Fixes
=========
Fixed a bug where graphical stats where not saved to the
temp file (maybe because MacOS 8.x).
Fixed usage of WSAPI_SendHTTPData (that problem was shown
by Chuck with its Server Fix Plugin). Welcome will not send
data to the client if the connection has dropped. Thanks Chuck!
Welcome now checks for the existance of a realm "pi_admin".
This was added for extra security.
The number of possible hosts was reduced from 10000 to 2000
to preserve some memory.
STILL TO DO: QuidProQuo does not support the Logging Role in
WSAPI. Welcome uses this role to collect hits for hit counting.
You will never see hits counted in QPQ 2.1 - until I found out
how to create a workaround, please be patient...
NEW: Do you like real hit statistics? Here they are:
Welcome now counts hits for every hour within the last 8 days;
for every day within the last 64 days and for every month of
the last 24 month. The only thing you need to do, is to enable
hit counting by checking the checkbox at each host page.
Access for stats is:
..../count.welcome?[domain name]/[selector]
and
[domain name] is either one of the virtual hosts
(e.g. "www.some.com") or the string "OverAll", which gives
you the total hit count and [selector] is either
• 0 = for today
• -1 up to -7 = yesterday, day before, ....
• day = daily counts for the last 64 days
• months = monthly counts for the last 24 month
Examples:
..../count.welcome?OverAll/0
..../count.welcome?OverAll/-4
..../count.welcome?www.aHost.com/days
..../count.welcome?www.aHost.com/months
It depends on your settings for private/public stats if these
calls will be protected with the hosts name/password or if they
are for public access. The OverAll call is protected by the
pi_admin name/password.
There are two new links to reset hit counters: one at the host
list to reset the overall counting and on each host page to reset
the hosts hits.
____________________________________________________________
What's new in 1.6b7:
Bugs & Fixes
=========
No bugs were fixed, because there were no bug reports yet.
NEW: One addition to the external files that were introduced
with b6 is, that you can have two values per line. The format
is now
value1<TAB>result
value2<TAB>result
value3<TAB>result
...
and if you use {#filename}, it will match any of the valueX
values. If there is a <TAB>result string after the value, the
corresponding <Xn> tag will not be the value but instead it
will be the "result". This will give you the ability to define
data pairs like name-password and a resulting string.
Example:
Path: /myDirectory*
Authorization: {#mypasswords}
Condition: <P0>&<!C0>
Path Result: <C1>
Redirect: checked
and the file "#mypasswords will be:
andreas:pardeike <TAB> http://www.somehost.com
james:dean <TAB> http://www.apple.com
...
NEW: The statistics can now be called separately for each
virtual host. Before, you could only call stats.welcome?n
(or pi_admin_stats.welcome?n for private access) with
n = 1..6.
Now you can use stats.welcome?n/virtual_host
with n=1...6 (jpeg quality) and
virtual_host = e.g. www.somehost.com
to show only the stats for www.somehost.com
NEW: There is an additional password you can configure
for each virtual host. If you set the stats to private, your
users can access their very own stats through:
..../stats.welcome?n/www.theirdomain.com (n=1...6)
Welcome protects this url with the configured password.
The password is entered like this: username:password
Of course, the full stats can only accessed through:
..../pi_admin_stats.welcome?n (n=1...6)
which only the webmaster knows the password.
____________________________________________________________
What's new in 1.6b6:
Bugs & Fixes
=========
No bugs were fixed, because there were no bug reports yet.
NEW: Now you can use {#filename} instead of
{valueA valueB valueC...}. There must be a file called
"#filename" inside the "Welcome-Plugin ƒ" folder. The
values in this file are separated by returns (like a one-field
export from FileMaker) and there is no limit to these values
but just the amount of free memory in your server application.
A good example is a check for robots. Assuming that you have
compiled a text file "#myrobotslist" you can write:
Browser: "*{#myrobotlist}*", which checks for many
text fragments in the browser type string. You can easily
update the values by editing the text file.
Note: the text files are checked while starting Welcome. You
can reload all text files with ..../pi_admin.welcome?reload
NEW: Welcome can now send the Authorization message
to get a new username/password combination from the
browser. Just choose "Authorization" at "Mode" on your
edit rule page. Then enter a realm name into the
Rule Result, like Rule Result: "MYREALM". If the Execute
Condition is true, Welcome will send a
"HTTP/1.0 401 Unauthorized" message when this rule is
executed. Here is an example:
Rule "My custom realm"
Path: *private*
Authorization: {#mypasswords}
Execute Condition: <P0>&<!C0>
Rule Result: MYREALM
Mode: (x) Authorization
Then create a file called "#mypasswords" and
enter:
Andreas:apassword
Peter:anotherpwd
Frank:hi
...
____________________________________________________________
What's new in 1.6b5:
Bugs & Fixes
=========
A major bug was fixed that will crash QuidProQuo (and
less likely but possible WebSTAR and others too).
Some minor bugs and misfunctions on how [] works are
now fixed.
NEW: You can combine * or | with [] or {} freely. An
example: To select windows/unix browsers, you can
now use "Browser: *{win NT unix dos}*" which previously
was not possible.
NEW: There are three new custom tags to use in the custom
field of each rule: "Authorization", "Client IP" and
"Client Name". Typical values to match for are e.g.:
Authorization: "username:password"
Client IP: "128.0.0.5"
Client Name: "host03.somedomain.org" (if not resolvable,
then the IP number is used in this field)
NEW: You don't need to encode "-", "^" or " " if you don't
use them inside [] or {} brackets anymore. E.g. you can
now write Path: "*cgi-bin*" instead of "*cgi\-bin*"
This is easier for beginners and not so restrictive.
____________________________________________________________
What's new in 1.6b4 (1.6b3 was never released):
Bugs & Fixes
==========
All variables initialized to default values. That fixes bugs
that appeared in QuidProQuo. Also fixed some really stupid
typos. This version should not crash anymore with QPQ.
Still to do: Support for *{}.
____________________________________________________________
What's new in 1.6b2:
Bugs & Fixes
=========
Several bugs and two memory leaks fixed. A bug in the main
header parsing shows that even Welcome 1.5 or older will
not handle requests like:
"GET /something.html<CR><LF><CR><LF>" correctly. This
is now fixed.
The Test-Page now correctly shows all extra values and
the file checking process. There is still a need to send
a full custom request to check ALL new features of Welcome.
Relative Path for "Missing Host Field (prefs page)"
=====================================
Now you can use a root relative path for the old
"Redirect instead of Missing Host Page" field at the prefs
page. Welcome will substitute the current value of the
incoming request path with this field. This enables you
to put a path to a script into this field and write all
information for the current request out to a file.
Example for this field: "/cgi-bin/myscript.acgi"
____________________________________________________________
What's new in 1.6b1:
Added extra tag field in Rules
==================
As the 6th field in Rules, you can enter your own tag name and
use it to make decisions or built path results on it.
You can access it by using the <Cn> reference, where n is as usual
n = 0...9.
I have added the reference names at the end of each tag field so
you can easily remember them.
Remember that you can put any name in the first field and you
don't have to include the colon (:). Here is an example:
"Pragma" : "no-cache"
will check for the browser sending "Pragma: no-cache" with
the request. Also a good example is to check for a password.
If you don't know which tags are send by a browser, you can
set WebSTAR to "Verbose Mode" and watch the log window.
This field is also very useful for checking a tag twice. E.g.
you could enter "Host" and have two lines for host checking.
FUTURE ENHANCEMENTS:
Currently, this field only support the real tags from the
request header. But I will add some more names that will
rely on:
- IP number or name of requestor
- decoded username/password
- date and time
If you can think of others, please mail me your suggestions
Added check for file existance
==================
The second improvement is a file check. For this, you can
use the two fields after the tag field section.
The first field is a condition field and it will allow you to
only check a file path if there is a need for it. This will save
cpu time. It is basically the same as the normal condition
field in the action section (that one that will control the
rule execution) and you can put strings like <H0>&<!P1>
into it.
The second field is a relative url path that is to be checked.
It need to start with a "/" and then should point to a file
that you like to check. This path is checked from the servers
root. You can (and should) use the tag references in this field
and it is good to keep in mind that it almost works like the
path result field. Here's an example:
File Path to check: "/subfolder/<P1>.lasso"
Welcome will ignore any $ or ? arguments and will only
check the real path portion of this field. Please note that
you cannot start this field with "http://server", it need
to be a RELATIVE path.
Finally, you can refer for the check (in the execute condition)
by using the reference "<FC>" (File Check) and it will result
in TRUE or FALSE depending on the existance of the checked
path.